Prerequisites for the Nodinite Boomi Monitoring agent

Prepare your environment for seamless, secure monitoring of Boomi integrations with Nodinite. This page details everything you need to install and run the Boomi Monitoring Agent, including software, network, firewall, and user rights requirements.

✅ Ensure compatibility with modern cloud and on-premise setups
✅ Meet all software and network prerequisites for reliable monitoring
✅ Secure your environment with proper firewall and user rights settings
✅ Benefit from proactive alerts and streamlined administration

You will learn how to:

• Install and configure the Boomi Monitoring Agent for Nodinite
• Set up required software and network access
• Apply best practices for security and administration

Instances of this agent can be installed on-premise using TCP/IP for local network access and/or in the cloud/off-site using Service Bus Relaying (see also the external link for additional information 'Azure Relay FAQs').

Tip

We recommend that you keep this agent close to the installation of Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)

Software Requirements

Versions 7.2.0 and later require .NET 10 Hosting Bundle. The Boomi Monitoring Agent can be deployed in two ways:

Deployment Option 1: IIS-Hosted Web Application (Recommended)

Typically installed on the Nodinite application server using Portal-based scripted installation.

Deployment Option 2: Windows Service (MSI Installer)

^{New 7.2.0}

For non-Nodinite server installations or specific Windows Service requirements.

Versions 7.2.0 and later require the .NET 10 Hosting Bundle—monthly updates are recommended to maintain security patches and performance improvements.
.NET 10 minimum OS: Windows Server 2012 / 2012 R2.
Versions 1.0.0.23 - 7.1.x use ASP.NET Core 8.0.
Versions 1.0.0.14 - 1.0.0.22 use .NET 7.
Versions prior to 1.0.0.14 use ASP.NET 5.

Important

IIS Deployment: You must download and install the ASP.NET Hosting Bundle. See Host ASP.NET Core on Windows with IIS.

Windows Service Deployment: Install the .NET 10 Hosting Bundle as well. It includes the .NET Runtime, so one installer covers both IIS and Windows Service hosting.

Supported Versions

Cloud technologies are evolving fast and Boomi deprecates older versions of their API's now and then. Nodinite will always support the API's supported by Boomi. This means you need to update Nodinite and the Boomi Monitoring Agent from time to time.

Make sure to subscribe to the Release Notes

AI Diagnostics

^{New 7.2.0}

Version 7.2.0 and later includes AI Diagnostics for intelligent error analysis and troubleshooting assistance. AI Diagnostics helps identify root causes of monitoring failures, suggests configuration fixes, and provides contextual guidance for common Boomi integration issues.

What AtomSphere User rights does the Nodinite Boomi Monitoring agent require?

• The agent uses the Atomsphere API to manage information and to modify the state of your Boomi Environment(s). Therefore the account used must be Administrator.
  

Role based security using least privileges are being evaluated, stay tuned.

What Windows User Rights does the Nodinite Boomi Monitoring agent require?

IIS-Hosted Deployment (Recommended)

The agent is installed as a Web Application within IIS, usually on the Nodinite application server. Virtual machines are supported.

• The App Pool can be configured to run with limited access rights.
  • The built-in ApplicationPoolIdentity can be used
    • During the installation, you must add the full control right for the IIS App Pool assigned to the Web Application.

    The specific settings are detailed on the Install the Nodinite Boomi Monitoring agent user guide.

Windows Service Deployment (MSI Installer)

^{New 7.2.0}

When using the MSI installer for Windows Service deployment, the agent requires:

Service Account Options:

• Group Managed Service Account (gMSA) - Recommended for automated password management. See Configure Group Managed Service Accounts (gMSA) for setup instructions.
• Traditional Account - Use a local named account or, preferably, a domain account.
  • Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.

What Firewall settings are required for the Nodinite Boomi Monitoring agent?

Where you install the Nodinite Boomi Monitoring Agent in relation to the Nodinite Monitoring Service and the Boomi AtomSphere API determines your firewall configuration. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.

Network diagram: the Monitoring Service calls the agent, and the agent calls the Boomi AtomSphere API over HTTPS; the agent never connects to your Atoms directly. Dashed arrows are optional hops.

Note

When the agent runs on the Core Services Server (the typical installation), you need no firewall rule between the Monitoring Service and the agent.

Between the Monitoring Service and the Boomi Monitoring agent

The Monitoring Service opens every connection; the agent never calls it. On Windows Server, Nodinite v7 hosts the agent as its own IIS web site, on a port you set per environment in the Nodinite Portal (Servers step).

Option: Service Bus Relaying (cloud or hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on different networks. Both sides connect outbound to the Azure Relay namespace, so neither server needs an inbound rule. Nodinite uses the same principle as the on-premises data gateway; see 'Adjust communication settings for the on-premises data gateway' and the 'Azure Relay FAQs'.

Between the Boomi Monitoring agent and the Boomi AtomSphere API

The agent calls the AtomSphere API to read the state of your Atoms, processes, and executions. All traffic is outbound HTTPS; Boomi needs no inbound rule. Allow the hostnames of your Boomi platform instance, as listed in Hostnames and IP Addresses for Platform.

Tip

Boomi Authentication: The agent requires an Administrator account to access the AtomSphere API. Role-based security with least privileges is being evaluated for future releases.

Tip

API Versioning: Boomi deprecates older API versions periodically. Update Nodinite and the Boomi Monitoring Agent regularly, and subscribe to the Release Notes.

Between the servers and DNS

Important

Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite Boomi Integrations Monitoring Agent exist in the Troubleshooting user guide.

Next Steps

Add or manage a Monitoring Agent Configuration
Install the Nodinite Boomi Monitoring agent

Related Topics

Monitoring Agents
Administration